Skip to main content

This is a new service – your feedback will help us to improve it.

Your data has issues

There is a problem

  • 1000 entries must have valid geometry
Reference Name Tree preservation order Uprn Address text Point Geometry Notes Felled date Entry date Start date End date
T9 - PS/540/15/150 T9

Unexpected geom type

2026-05-23
T11 - PS/540/15/150 T11

Unexpected geom type

2026-05-23
T15 - PS/540/15/150 T15

Unexpected geom type

2026-05-23
T14 - PS/540/15/150 T14

Unexpected geom type

2026-05-23
T13 - PS/540/15/150 T13

Unexpected geom type

2026-05-23
T12 - PS/540/15/150 T12

Unexpected geom type

2026-05-23
T6 - PS/540/15/151 T6

Unexpected geom type

2026-05-23
T5 - PS/540/15/151 T5

Unexpected geom type

2026-05-23
T4 - PS/540/15/151 T4

Unexpected geom type

2026-05-23
T3 - PS/540/15/151 T3

Unexpected geom type

2026-05-23
T2 - PS/540/15/151 T2

Unexpected geom type

2026-05-23
T1 - PS/540/15/151 T1

Unexpected geom type

2026-05-23
T1 - PS/540/15/150 T1

Unexpected geom type

2026-05-23
T2 - PS/540/15/150 T2

Unexpected geom type

2026-05-23
T5 - PS/540/15/150 T5

Unexpected geom type

2026-05-23
T1 - PS/540/15/161 T1

Unexpected geom type

2026-05-23
T10 - PS/540/15/165 T10

Unexpected geom type

2026-05-23
T25 - PS/540/15/165 T25

Unexpected geom type

2026-05-23
T3 - PS/540/15/128 T3

Unexpected geom type

2026-05-23
T11 - PS/540/15/165 T11

Unexpected geom type

2026-05-23
T20 - PS/540/15/165 T20

Unexpected geom type

2026-05-23
T21 - PS/540/15/165 T21

Unexpected geom type

2026-05-23
T18 - PS/540/15/165 T18

Unexpected geom type

2026-05-23
T19 - PS/540/15/165 T19

Unexpected geom type

2026-05-23
T16 - PS/540/15/165 T16

Unexpected geom type

2026-05-23
T17 - PS/540/15/165 T17

Unexpected geom type

2026-05-23
T6 - PS/540/15/165 T6

Unexpected geom type

2026-05-23
T7 - PS/540/15/165 T7

Unexpected geom type

2026-05-23
T4 - PS/540/15/165 T4

Unexpected geom type

2026-05-23
T5 - PS/540/15/165 T5

Unexpected geom type

2026-05-23
T3 - PS/540/15/165 T3

Unexpected geom type

2026-05-23
T2 - PS/540/15/165 T2

Unexpected geom type

2026-05-23
T1 - PS/540/15/165 T1

Unexpected geom type

2026-05-23
T8 - PS/540/15/165 T8

Unexpected geom type

2026-05-23
T9 - PS/540/15/165 T9

Unexpected geom type

2026-05-23
T14 - PS/540/15/165 T14

Unexpected geom type

2026-05-23
T15 - PS/540/15/165 T15

Unexpected geom type

2026-05-23
T26 - PS/540/15/165 T26

Unexpected geom type

2026-05-23
T12 - PS/540/15/165 T12

Unexpected geom type

2026-05-23
T13 - PS/540/15/165 T13

Unexpected geom type

2026-05-23
T4 - PS/540/15/168 T4

Unexpected geom type

2026-05-23
T5 - PS/540/15/168 T5

Unexpected geom type

2026-05-23
T2 - PS/540/15/168 T2

Unexpected geom type

2026-05-23
T3 - PS/540/15/168 T3

Unexpected geom type

2026-05-23
T13 - PS/540/15/168 T13

Unexpected geom type

2026-05-23
T1 - PS/540/15/168 T1

Unexpected geom type

2026-05-23
T10 - PS/540/15/168 T10

Unexpected geom type

2026-05-23
T11 - PS/540/15/168 T11

Unexpected geom type

2026-05-23
T8 - PS/540/15/168 T8

Unexpected geom type

2026-05-23
T9 - PS/540/15/168 T9

Unexpected geom type

2026-05-23

Showing rows 701 to 750 of 1000

How to fix this issue

Your data is missing a geometry.

The Tree guidance explains how to fix the issue:

geometry

The boundary of the tree as a single polygon or multipolygon value. All points in the polygon must be in the WGS84 coordinate reference system.

If you’re providing geometry in a CSV, geometry should be in well-known text (WKT).

You must provide a point or geometry for each tree. You may provide both.

Example: MULTIPOLYGON (((1.188829 51.23478,1.188376 51.234909,1.188381 51.234917,1.187912 51.235022...

If you’re providing geometry in a GeoJSON, GML or Geopackage, use the associated geometry format.

How to improve Milton Keynes City Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL